DBusConnection.callWithUnixFdList

Like g_dbus_connection_call() but also takes a #GUnixFDList object.

The file descriptors normally correspond to %G_VARIANT_TYPE_HANDLE values in the body of the message. For example, if a message contains two file descriptors, @fd_list would have length 2, and g_variant_new_handle (0) and g_variant_new_handle (1) would appear somewhere in the body of the message (not necessarily in that order!) to represent the file descriptors at indexes 0 and 1 respectively.

When designing D-Bus APIs that are intended to be interoperable, please note that non-GDBus implementations of D-Bus can usually only access file descriptors if they are referenced in this way by a value of type %G_VARIANT_TYPE_HANDLE in the body of the message.

This method is only available on UNIX.

Parameters

busName string

a unique or well-known bus name or %NULL if @connection is not a message bus connection

objectPath string

path of remote object

interfaceName string

D-Bus interface to invoke method on

methodName string

the name of the method to invoke

parameters Variant

a #GVariant tuple with parameters for the method or %NULL if not passing parameters

replyType VariantType

the expected type of the reply, or %NULL

flags GDBusCallFlags

flags from the #GDBusCallFlags enumeration

timeoutMsec int

the timeout in milliseconds, -1 to use the default timeout or %G_MAXINT for no timeout

fdList UnixFDList

a #GUnixFDList or %NULL

cancellable Cancellable

a #GCancellable or %NULL

callback GAsyncReadyCallback

a #GAsyncReadyCallback to call when the request is satisfied or %NULL if you don't * care about the result of the method invocation

userData void*

The data to pass to @callback.

Meta

Since

2.30